The term keyctionary is made of the words keyword and dictionary. It denotes a dictionary storing names to be declared as keywords in the programming language the source code to be vahunzed is written in.
In this context, keyword means pretty much anything that is a
reserved word. In ANSI C, this for example applies to
while, include of #include and
ul of int sepp = 123ul.
Compiler specific keywords like __inline__ or
far are not stored in the keyctionary but rather in the
dignorary.
The keyctionary is not yet another file floating around. Instead, Vahunz already has internal ones and decides which one to use depending on the programming language the source code is written in.
To find out the programming language used, Vahunz looks at the suffices of all files to be vahunzed. The following suffices are recognized:
| Suffix | Language |
|---|---|
| c, h | C (both ANSI and K&R) |
| c++, cpp, cxx, cc | C++ |
| java | Java |
The suffix comparison is case insensitive.
The same programming language has to be used for all files. That means, you can not vahunz C and Java together, as C has reserved words Java does not have, and the other way round.
An exception of this is C and C++. If source codes in both languages show up, C++'s reserved words will be used even on the plain C sources.